Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af189ea0d182441f970d61e3c47bdd1d2c61dfd6e15882f4a3b129304e6adc1b

Tx prefix hash: 71e74b0368b76768ab2d5c8f7e17026de578d41d3460ebf491c5ed1571e15010
Tx public key: dc94a00d446026b5b6da27493de6eb0cc306d567bd0bb8a74e287afabea185f7
Timestamp: 1760396710 Timestamp [UCT]: 2025-10-13 23:05:10 Age [y:d:h:m:s]: 00:028:07:23:46
Block: 1389361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20251 RingCT/type: yes/0
Extra: 01dc94a00d446026b5b6da27493de6eb0cc306d567bd0bb8a74e287afabea185f7021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4746dc39f5f190cd9cde65b9cb3aa136f94af07c7653d03eb748b328d4c0b846 0.600000000000 1877590 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": 1389371, "vin": [ { "gen": { "height": 1389361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4746dc39f5f190cd9cde65b9cb3aa136f94af07c7653d03eb748b328d4c0b846" } } ], "extra": [ 1, 220, 148, 160, 13, 68, 96, 38, 181, 182, 218, 39, 73, 61, 230, 235, 12, 195, 6, 213, 103, 189, 11, 184, 167, 78, 40, 122, 250, 190, 161, 133, 247, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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