Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a84a583b891048c1b53dad3844dfccd119dfce21c5432e2d51743a9c999d63f

Tx prefix hash: 08432b9314f371afd669ba9f17f61a4841cc10c00b63685fa81711d6b575d902
Tx public key: ef52b9628fc7d429632e5d81142d0dc0b95f67d41c24691639dc82dc34afb40f
Timestamp: 1714413977 Timestamp [UCT]: 2024-04-29 18:06:17 Age [y:d:h:m:s]: 00:341:23:42:25
Block: 1011235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244467 RingCT/type: yes/0
Extra: 01ef52b9628fc7d429632e5d81142d0dc0b95f67d41c24691639dc82dc34afb40f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 636c63750ac7490dad1931b0aae816d54a8e35bc30374f6077606e7d3275cd0c 0.600000000000 1473413 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": 1011245, "vin": [ { "gen": { "height": 1011235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "636c63750ac7490dad1931b0aae816d54a8e35bc30374f6077606e7d3275cd0c" } } ], "extra": [ 1, 239, 82, 185, 98, 143, 199, 212, 41, 99, 46, 93, 129, 20, 45, 13, 192, 185, 95, 103, 212, 28, 36, 105, 22, 57, 220, 130, 220, 52, 175, 180, 15, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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