Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aefd7725ad51db20076f8e045357cd9797113c939642ad129c03b38ac0882bbe

Tx prefix hash: fc83da509991941121ca1c1b9090a0af8f84d249f462f316ad5ddec0c1413369
Tx public key: 7bf1f6e1ca6dd9e48c3d80e823a951113e0475dae62bcd26592753a32249b927
Timestamp: 1705071938 Timestamp [UCT]: 2024-01-12 15:05:38 Age [y:d:h:m:s]: 01:073:22:47:09
Block: 933781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313943 RingCT/type: yes/0
Extra: 017bf1f6e1ca6dd9e48c3d80e823a951113e0475dae62bcd26592753a32249b92702110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6260b44f09ac29a05f0bf3d7e6ed05eed2f8a462f4acb5e875b9e0bba8ee7a6 0.600000000000 1391759 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": 933791, "vin": [ { "gen": { "height": 933781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6260b44f09ac29a05f0bf3d7e6ed05eed2f8a462f4acb5e875b9e0bba8ee7a6" } } ], "extra": [ 1, 123, 241, 246, 225, 202, 109, 217, 228, 140, 61, 128, 232, 35, 169, 81, 17, 62, 4, 117, 218, 230, 43, 205, 38, 89, 39, 83, 163, 34, 73, 185, 39, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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