Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510b6bcf0fe647c2d21ecb2b773a066aa427b8f210d79774f0447035aa260bfa

Tx prefix hash: fd4ae526334a6355d90e7c28b534dded1f68f2d0d51d912bc900b592f10d2c9e
Tx public key: dfe36862fbc5112daf5dce8c5f73442cd792e4c762640a372ecf927b0eeab30c
Timestamp: 1725199014 Timestamp [UCT]: 2024-09-01 13:56:54 Age [y:d:h:m:s]: 00:245:22:22:12
Block: 1100660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175635 RingCT/type: yes/0
Extra: 01dfe36862fbc5112daf5dce8c5f73442cd792e4c762640a372ecf927b0eeab30c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7733b24f3ca654a6a748f5bdc37e8793b2ea1be9cff579087c855df558af47c1 0.600000000000 1576639 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": 1100670, "vin": [ { "gen": { "height": 1100660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7733b24f3ca654a6a748f5bdc37e8793b2ea1be9cff579087c855df558af47c1" } } ], "extra": [ 1, 223, 227, 104, 98, 251, 197, 17, 45, 175, 93, 206, 140, 95, 115, 68, 44, 215, 146, 228, 199, 98, 100, 10, 55, 46, 207, 146, 123, 14, 234, 179, 12, 2, 17, 0, 0, 0, 6, 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