Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e95963cf71def5815e9bdd57e72339829fe90f32dc3e38130456c6ba5510c2

Tx prefix hash: 69e99d5ace60dd792618ba9e7586ea4a67e1fbbdc28fe1d36407dc42300e1112
Tx public key: c861d6fabbc445c7092c531635249c5b18e1d10392b1357874eb7a66e8a7ab27
Timestamp: 1724324441 Timestamp [UCT]: 2024-08-22 11:00:41 Age [y:d:h:m:s]: 00:297:00:19:53
Block: 1093428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212072 RingCT/type: yes/0
Extra: 01c861d6fabbc445c7092c531635249c5b18e1d10392b1357874eb7a66e8a7ab27021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f33f3dba6076deefee51b4a2c1183570fa14e7e38f05651e7fd30a0d2c7de21 0.600000000000 1568367 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": 1093438, "vin": [ { "gen": { "height": 1093428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f33f3dba6076deefee51b4a2c1183570fa14e7e38f05651e7fd30a0d2c7de21" } } ], "extra": [ 1, 200, 97, 214, 250, 187, 196, 69, 199, 9, 44, 83, 22, 53, 36, 156, 91, 24, 225, 209, 3, 146, 177, 53, 120, 116, 235, 122, 102, 232, 167, 171, 39, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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