Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 734ac16482c25fd4465b5b30849e7a27e9dd539416d0d29c8a2f312b4821087c

Tx prefix hash: 4a316054febe698ae93201f27d28a180e2e65b831c184e080b59b3c73400424d
Tx public key: 6b2cef0cdbd9575386a0ecb7854df98be17dc949cd6fb296592ab7456431caec
Timestamp: 1578236523 Timestamp [UCT]: 2020-01-05 15:02:03 Age [y:d:h:m:s]: 05:105:15:48:17
Block: 39270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1225410 RingCT/type: yes/0
Extra: 016b2cef0cdbd9575386a0ecb7854df98be17dc949cd6fb296592ab7456431caec021100000008d81c26c0000000000000000000

1 output(s) for total of 454.865540460000 dcy

stealth address amount amount idx
00: 6ce5e333702c5f13dbaad37aeb09f0866ad88b0f94c66c76a37c4a3db03c8a24 454.865540460000 67581 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": 39280, "vin": [ { "gen": { "height": 39270 } } ], "vout": [ { "amount": 454865540460, "target": { "key": "6ce5e333702c5f13dbaad37aeb09f0866ad88b0f94c66c76a37c4a3db03c8a24" } } ], "extra": [ 1, 107, 44, 239, 12, 219, 217, 87, 83, 134, 160, 236, 183, 133, 77, 249, 139, 225, 125, 201, 73, 205, 111, 178, 150, 89, 42, 183, 69, 100, 49, 202, 236, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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