Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f7cd8bb35d72b7e26ac7c8df1ffc9e4ef9747cb6ae78684bcb4350db95db6a

Tx prefix hash: f4583011b5e0cc8cd9386797bc88814935c3105cc5bc70e6a5756830b9c7d03a
Tx public key: f6887b9373c760e90a3a47c7d602fbed7da12aa09e7fd4b9157a54593847f9d6
Timestamp: 1743806510 Timestamp [UCT]: 2025-04-04 22:41:50 Age [y:d:h:m:s]: 00:292:01:41:32
Block: 1254422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206420 RingCT/type: yes/0
Extra: 01f6887b9373c760e90a3a47c7d602fbed7da12aa09e7fd4b9157a54593847f9d60211000000064060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4bf6f64325e309a0ff853a9f9b70ea1b1fb6ad16b64ef449ad3984c225afb6e 0.600000000000 1741503 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": 1254432, "vin": [ { "gen": { "height": 1254422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4bf6f64325e309a0ff853a9f9b70ea1b1fb6ad16b64ef449ad3984c225afb6e" } } ], "extra": [ 1, 246, 136, 123, 147, 115, 199, 96, 233, 10, 58, 71, 199, 214, 2, 251, 237, 125, 161, 42, 160, 158, 127, 212, 185, 21, 122, 84, 89, 56, 71, 249, 214, 2, 17, 0, 0, 0, 6, 64, 96, 246, 210, 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