Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0379a0170b37762b565fe5a34325cd0dc72c031e4f6f81cf983ba11f2b7ed295

Tx prefix hash: 435bff901b4910fa3d26be5c8d21adc46093d6936b03c218a40d02455a2b8683
Tx public key: 1a807e254e047d0c30d455503fc4a1d87e33bce292334f97273aee0a459dd31b
Timestamp: 1575932335 Timestamp [UCT]: 2019-12-09 22:58:55 Age [y:d:h:m:s]: 05:062:01:23:28
Block: 24253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190178 RingCT/type: yes/0
Extra: 011a807e254e047d0c30d455503fc4a1d87e33bce292334f97273aee0a459dd31b0211000000129159db1e000000000000000000

1 output(s) for total of 510.082723004000 dcy

stealth address amount amount idx
00: 921a95d2d5a1b70338ebad3f374f6a2f29c117f4e50893d454ba21ba21c1a3d3 510.082723004000 39828 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": 24263, "vin": [ { "gen": { "height": 24253 } } ], "vout": [ { "amount": 510082723004, "target": { "key": "921a95d2d5a1b70338ebad3f374f6a2f29c117f4e50893d454ba21ba21c1a3d3" } } ], "extra": [ 1, 26, 128, 126, 37, 78, 4, 125, 12, 48, 212, 85, 80, 63, 196, 161, 216, 126, 51, 188, 226, 146, 51, 79, 151, 39, 58, 238, 10, 69, 157, 211, 27, 2, 17, 0, 0, 0, 18, 145, 89, 219, 30, 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