Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d2d71fee1b2540325735b4dbe728fe580112355652c62f06ae4d3dc096537f

Tx prefix hash: bcb6ca4976e7234f0287ebe029647cfa65dc2b0cc500c7b72acbed47d02c8c58
Tx public key: b4bb6c661c1bbae81ac6ac49a016e3b2d5fab88abc2e4d4ded64bf0114c2fbb3
Timestamp: 1754355858 Timestamp [UCT]: 2025-08-05 01:04:18 Age [y:d:h:m:s]: 00:178:06:06:59
Block: 1340449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126296 RingCT/type: yes/0
Extra: 01b4bb6c661c1bbae81ac6ac49a016e3b2d5fab88abc2e4d4ded64bf0114c2fbb302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354991bb5069e568c165eec5732f66568a92b571f813ab67a1dcbaaaefa8e82d 0.600000000000 1828266 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": 1340459, "vin": [ { "gen": { "height": 1340449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354991bb5069e568c165eec5732f66568a92b571f813ab67a1dcbaaaefa8e82d" } } ], "extra": [ 1, 180, 187, 108, 102, 28, 27, 186, 232, 26, 198, 172, 73, 160, 22, 227, 178, 213, 250, 184, 138, 188, 46, 77, 77, 237, 100, 191, 1, 20, 194, 251, 179, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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