Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c00dee41086a6e74297bc5f6ca2c303a15e262d6be5a485f70e7dc1a46e2e5

Tx prefix hash: 51c2a1107b6535a8044b559d51c6c54ce6a0a2134d1f269b8ad646d5313ca45a
Tx public key: 0f13b6c3ff1bf30ae092568c6d5be1a04a1c2d4220c332bbb1f30f6035fff53e
Timestamp: 1723267693 Timestamp [UCT]: 2024-08-10 05:28:13 Age [y:d:h:m:s]: 00:237:12:39:20
Block: 1084647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169644 RingCT/type: yes/0
Extra: 010f13b6c3ff1bf30ae092568c6d5be1a04a1c2d4220c332bbb1f30f6035fff53e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ae3d41af957bf042c92fa2826a9b4db49dde3d7316ef58cf56e9e25ed17dd92 0.600000000000 1559000 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": 1084657, "vin": [ { "gen": { "height": 1084647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ae3d41af957bf042c92fa2826a9b4db49dde3d7316ef58cf56e9e25ed17dd92" } } ], "extra": [ 1, 15, 19, 182, 195, 255, 27, 243, 10, 224, 146, 86, 140, 109, 91, 225, 160, 74, 28, 45, 66, 32, 195, 50, 187, 177, 243, 15, 96, 53, 255, 245, 62, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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