Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a1ecc4a40b5333c91faf89b6ff8fc2fa7920f65a1dd305dcc7688b240045d1a

Tx prefix hash: 1ae594a520954e17063e187d3ab2b709cd8503200c5975e75a41bd5876757706
Tx public key: 2519a5300773d6b13fe31e02f9046c5f9a73f84e3bb3c7025b94837efbbb033b
Timestamp: 1698934415 Timestamp [UCT]: 2023-11-02 14:13:35 Age [y:d:h:m:s]: 02:005:13:04:19
Block: 883123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523526 RingCT/type: yes/0
Extra: 012519a5300773d6b13fe31e02f9046c5f9a73f84e3bb3c7025b94837efbbb033b02110000000933af99f4000000000000000000

1 output(s) for total of 0.727523301000 dcy

stealth address amount amount idx
00: bc2d4e7a75323d0f585a06d1d3122c2677cd16469ca255c25e10e46d65a36874 0.727523301000 1338811 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": 883133, "vin": [ { "gen": { "height": 883123 } } ], "vout": [ { "amount": 727523301, "target": { "key": "bc2d4e7a75323d0f585a06d1d3122c2677cd16469ca255c25e10e46d65a36874" } } ], "extra": [ 1, 37, 25, 165, 48, 7, 115, 214, 177, 63, 227, 30, 2, 249, 4, 108, 95, 154, 115, 248, 78, 59, 179, 199, 2, 91, 148, 131, 126, 251, 187, 3, 59, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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