Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f8482f78eb0fd7d6c9340a49097f3537979b151ec9f908b86e9990f8c510f7

Tx prefix hash: 2f3f9115e4047ae78fa358e787eb642fabae20f374655baf54b41fc2a598dfb5
Tx public key: 520440da9ed22e5a4dc5dc9ae2dff9748625a845feed297708a4bbe7cbca728d
Timestamp: 1762977584 Timestamp [UCT]: 2025-11-12 19:59:44 Age [y:d:h:m:s]: 00:039:20:41:59
Block: 1410736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28542 RingCT/type: yes/0
Extra: 01520440da9ed22e5a4dc5dc9ae2dff9748625a845feed297708a4bbe7cbca728d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eafda99c15e6fdadc34f9a3116ab013fb21d8da7e18dcc5d0e43a9c32449a3f4 0.600000000000 1899189 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": 1410746, "vin": [ { "gen": { "height": 1410736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eafda99c15e6fdadc34f9a3116ab013fb21d8da7e18dcc5d0e43a9c32449a3f4" } } ], "extra": [ 1, 82, 4, 64, 218, 158, 210, 46, 90, 77, 197, 220, 154, 226, 223, 249, 116, 134, 37, 168, 69, 254, 237, 41, 119, 8, 164, 187, 231, 203, 202, 114, 141, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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