Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 604d739d9e31574dea73b30baf948e9e9d2bae250fbf3718574a7f794ba64b61

Tx prefix hash: fbb390b3772fc1a8edf3c643005ec3b98d755760934dc39e0fcf5f9e6a2a218a
Tx public key: f7009dcaf02063708eb393c613dc9c3bdb690373afa9159e4ca7932bd5a86ed8
Timestamp: 1762578867 Timestamp [UCT]: 2025-11-08 05:14:27 Age [y:d:h:m:s]: 00:045:08:57:34
Block: 1407436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32473 RingCT/type: yes/0
Extra: 01f7009dcaf02063708eb393c613dc9c3bdb690373afa9159e4ca7932bd5a86ed8021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c37f1362982aca2ae5c9b7d88c2dbbab0b0d20c5da06239a383d9534ca87a4cb 0.600000000000 1895857 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": 1407446, "vin": [ { "gen": { "height": 1407436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c37f1362982aca2ae5c9b7d88c2dbbab0b0d20c5da06239a383d9534ca87a4cb" } } ], "extra": [ 1, 247, 0, 157, 202, 240, 32, 99, 112, 142, 179, 147, 198, 19, 220, 156, 59, 219, 105, 3, 115, 175, 169, 21, 158, 76, 167, 147, 43, 213, 168, 110, 216, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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