Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9532fcb35ceb8a5e70403cb806e0f4247ecd4d1af46f6f1a44a5cd86cd84cb43

Tx prefix hash: 3ec6329b6f72c3d17eb76fe81f469e868a67771dfaacd3826687c8674ed4d2e5
Tx public key: b52614e1baa6a571560d2e0fe52fc00975301792190da25ba1de6a22fc1d5838
Timestamp: 1730034354 Timestamp [UCT]: 2024-10-27 13:05:54 Age [y:d:h:m:s]: 00:085:18:16:52
Block: 1140699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61284 RingCT/type: yes/0
Extra: 01b52614e1baa6a571560d2e0fe52fc00975301792190da25ba1de6a22fc1d5838021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 721ade11e44cfb0dce8d2c6bd7b0c293cc9f3b396fa1579dcd0d9b0e9b04f7db 0.600000000000 1624502 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": 1140709, "vin": [ { "gen": { "height": 1140699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "721ade11e44cfb0dce8d2c6bd7b0c293cc9f3b396fa1579dcd0d9b0e9b04f7db" } } ], "extra": [ 1, 181, 38, 20, 225, 186, 166, 165, 113, 86, 13, 46, 15, 229, 47, 192, 9, 117, 48, 23, 146, 25, 13, 162, 91, 161, 222, 106, 34, 252, 29, 88, 56, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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