Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f4f6fb25cb41a8fae9567a61a5af1d98e361dedd8344ab4a640958d4199745

Tx prefix hash: 01fa259186cc3b7ce7a2273f69104d3325539774f962909f5ea21803a2a1309f
Tx public key: bdd24ea603cf467872cdab4a4b31b7f94756b4a39ed86a85bd9f4616878d6fd2
Timestamp: 1710297582 Timestamp [UCT]: 2024-03-13 02:39:42 Age [y:d:h:m:s]: 01:325:18:04:53
Block: 977130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491450 RingCT/type: yes/0
Extra: 01bdd24ea603cf467872cdab4a4b31b7f94756b4a39ed86a85bd9f4616878d6fd20211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5b530671394d1f54426c6433780452dba3cc89eaf6663f9b387518b38426c6 0.600000000000 1437131 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": 977140, "vin": [ { "gen": { "height": 977130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5b530671394d1f54426c6433780452dba3cc89eaf6663f9b387518b38426c6" } } ], "extra": [ 1, 189, 210, 78, 166, 3, 207, 70, 120, 114, 205, 171, 74, 75, 49, 183, 249, 71, 86, 180, 163, 158, 216, 106, 133, 189, 159, 70, 22, 135, 141, 111, 210, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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