Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2612e1be7e6b6a6f59a1af6c9d678acf7ab1c2c28c13ae00667caea2445f22ac

Tx prefix hash: abb0b04927fca71deb810314fd91e3d88b77412d58acecc89f2c29e02884dcd5
Tx public key: 918c012c3b77c7f7572883c95184b82ac0e6e38b97c874e7cb90db164a641ca7
Timestamp: 1707180476 Timestamp [UCT]: 2024-02-06 00:47:56 Age [y:d:h:m:s]: 00:228:12:04:28
Block: 951264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163696 RingCT/type: yes/0
Extra: 01918c012c3b77c7f7572883c95184b82ac0e6e38b97c874e7cb90db164a641ca702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63204a331a05eb6604d945d0c80001ffedfc438713b538d3676e741715b6ccc7 0.600000000000 1410004 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": 951274, "vin": [ { "gen": { "height": 951264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63204a331a05eb6604d945d0c80001ffedfc438713b538d3676e741715b6ccc7" } } ], "extra": [ 1, 145, 140, 1, 44, 59, 119, 199, 247, 87, 40, 131, 201, 81, 132, 184, 42, 192, 230, 227, 139, 151, 200, 116, 231, 203, 144, 219, 22, 74, 100, 28, 167, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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