Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c10d929c3f8bc266b24625053b454a040fdbde467b9d495e46854f436afc262d

Tx prefix hash: ffaef4c0f58a731710726010bb36a08072044e325c866525211f0462712fb73d
Tx public key: 1a614552e5f1a5af68c465350e70f25a0bc433c570e31d8cfddef0beeab10112
Timestamp: 1577840320 Timestamp [UCT]: 2020-01-01 00:58:40 Age [y:d:h:m:s]: 04:361:23:51:45
Block: 36074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147868 RingCT/type: yes/0
Extra: 011a614552e5f1a5af68c465350e70f25a0bc433c570e31d8cfddef0beeab10112021100000024398c17aa000000000000000000

1 output(s) for total of 466.093145753000 dcy

stealth address amount amount idx
00: 340b2c8e094a3c735c694366b9a894ab1edfbab459ffd975940e01b4d026a71d 466.093145753000 60982 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 36084, "vin": [ { "gen": { "height": 36074 } } ], "vout": [ { "amount": 466093145753, "target": { "key": "340b2c8e094a3c735c694366b9a894ab1edfbab459ffd975940e01b4d026a71d" } } ], "extra": [ 1, 26, 97, 69, 82, 229, 241, 165, 175, 104, 196, 101, 53, 14, 112, 242, 90, 11, 196, 51, 197, 112, 227, 29, 140, 253, 222, 240, 190, 234, 177, 1, 18, 2, 17, 0, 0, 0, 36, 57, 140, 23, 170, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8