Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 535b73a365b3acf7929343ee2a03d961ce9bcc3de703a53f34c68ef4f20e2949

Tx prefix hash: 84429f093525c6f41e0e945e439dcd4b73f782dad7ea6f62400d3a3bc2996bcd
Tx public key: 77bf148dd8a2ea1114a395b367d1874046cfc2e715f26c04ec881ad33cb40b78
Timestamp: 1734894026 Timestamp [UCT]: 2024-12-22 19:00:26 Age [y:d:h:m:s]: 00:177:11:51:24
Block: 1180945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126542 RingCT/type: yes/0
Extra: 0177bf148dd8a2ea1114a395b367d1874046cfc2e715f26c04ec881ad33cb40b780211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d5ff3ee1573f2877281346c1308181a37ae1bb7354d8e6cda3e91bbea3c214b 0.600000000000 1667360 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": 1180955, "vin": [ { "gen": { "height": 1180945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d5ff3ee1573f2877281346c1308181a37ae1bb7354d8e6cda3e91bbea3c214b" } } ], "extra": [ 1, 119, 191, 20, 141, 216, 162, 234, 17, 20, 163, 149, 179, 103, 209, 135, 64, 70, 207, 194, 231, 21, 242, 108, 4, 236, 136, 26, 211, 60, 180, 11, 120, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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