Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8241ec7e98db56ac0c60098f20537f8507c5210cf3c3237a4243a7e22c5f1fd9

Tx prefix hash: 608e6248cb9c18967f2491d851b3899aab7e5241c1a3f26110d61e9fe155c34e
Tx public key: 0e0edcee7da535d42541ab94b1b4dee82a7ce3e055d0f368e5276cbb2e348bf0
Timestamp: 1582972474 Timestamp [UCT]: 2020-02-29 10:34:34 Age [y:d:h:m:s]: 04:302:19:49:17
Block: 73936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110178 RingCT/type: yes/0
Extra: 010e0edcee7da535d42541ab94b1b4dee82a7ce3e055d0f368e5276cbb2e348bf002110000018fc71d3ff9000000000000000000

1 output(s) for total of 349.162545734000 dcy

stealth address amount amount idx
00: b2d5f4f7928b8681ce59bd9393189692fee2004b2e7be48e6493d881baccb496 349.162545734000 136635 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": 73946, "vin": [ { "gen": { "height": 73936 } } ], "vout": [ { "amount": 349162545734, "target": { "key": "b2d5f4f7928b8681ce59bd9393189692fee2004b2e7be48e6493d881baccb496" } } ], "extra": [ 1, 14, 14, 220, 238, 125, 165, 53, 212, 37, 65, 171, 148, 177, 180, 222, 232, 42, 124, 227, 224, 85, 208, 243, 104, 229, 39, 108, 187, 46, 52, 139, 240, 2, 17, 0, 0, 1, 143, 199, 29, 63, 249, 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