Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49e8d454813186704e634d252d9333d47ad9d9f704919a6ca821e89ec058c46f

Tx prefix hash: a43d54a7d0f60082afcc4a96cef1e5099ca66be33389f741e5c156fdc41208a6
Tx public key: 374aba6f16679f08e8e322399c3168f58cc9cee5cbd0a50b605b07b72bdf87cc
Timestamp: 1721224657 Timestamp [UCT]: 2024-07-17 13:57:37 Age [y:d:h:m:s]: 00:129:21:19:56
Block: 1067719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92928 RingCT/type: yes/0
Extra: 01374aba6f16679f08e8e322399c3168f58cc9cee5cbd0a50b605b07b72bdf87cc02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b0c9f54b7604ad666f78d6695c3ce021bd5ca6b8d351081960f4f17fc35a39 0.600000000000 1538610 of 15

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": 1067729, "vin": [ { "gen": { "height": 1067719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b0c9f54b7604ad666f78d6695c3ce021bd5ca6b8d351081960f4f17fc35a39" } } ], "extra": [ 1, 55, 74, 186, 111, 22, 103, 159, 8, 232, 227, 34, 57, 156, 49, 104, 245, 140, 201, 206, 229, 203, 208, 165, 11, 96, 91, 7, 183, 43, 223, 135, 204, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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