Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54b5f95cf9d185d7343f72bb05588f8b30b3adca89acb18ebb2f4db1eed5ab2c

Tx prefix hash: 85077868a3e7b3fad813c82bad01317a73608367e0678fe9319c6abb5b3df5d8
Tx public key: 2b0d4a6b9a5c670d370fc247caca2c4627fd53a2c55b0dbfe360313192b981cc
Timestamp: 1737629020 Timestamp [UCT]: 2025-01-23 10:43:40 Age [y:d:h:m:s]: 00:328:05:58:35
Block: 1203508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232190 RingCT/type: yes/0
Extra: 012b0d4a6b9a5c670d370fc247caca2c4627fd53a2c55b0dbfe360313192b981cc02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ca1dc39755c02d047e92ebb398140c0a11b2f4ce233a83bd3a94de474d47a6a 0.600000000000 1690185 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": 1203518, "vin": [ { "gen": { "height": 1203508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ca1dc39755c02d047e92ebb398140c0a11b2f4ce233a83bd3a94de474d47a6a" } } ], "extra": [ 1, 43, 13, 74, 107, 154, 92, 103, 13, 55, 15, 194, 71, 202, 202, 44, 70, 39, 253, 83, 162, 197, 91, 13, 191, 227, 96, 49, 49, 146, 185, 129, 204, 2, 17, 0, 0, 0, 13, 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