Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d45f4db8650549ff577b2eef77fff90e4cfb8ca411e4df7889e93747de98388

Tx prefix hash: 59d5f65cac4f41fded81b136696966a8c52fb224983752a429e68772d20d7599
Tx public key: 1e62f3cfbf5e5689ee5ea6ed7284fb66b4dcb907dc84448a2aee1fd461162387
Timestamp: 1702742069 Timestamp [UCT]: 2023-12-16 15:54:29 Age [y:d:h:m:s]: 01:035:00:22:06
Block: 914476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286349 RingCT/type: yes/0
Extra: 011e62f3cfbf5e5689ee5ea6ed7284fb66b4dcb907dc84448a2aee1fd461162387021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d736efdd631cb1426062227bf3f3c011efd20713dca543716f4ccd45dd3e2a2 0.600000000000 1371792 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": 914486, "vin": [ { "gen": { "height": 914476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d736efdd631cb1426062227bf3f3c011efd20713dca543716f4ccd45dd3e2a2" } } ], "extra": [ 1, 30, 98, 243, 207, 191, 94, 86, 137, 238, 94, 166, 237, 114, 132, 251, 102, 180, 220, 185, 7, 220, 132, 68, 138, 42, 238, 31, 212, 97, 22, 35, 135, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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