Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf03e4c17c7bb33296d871b79715b0f3566cd1fd9231dbcbc0ac9a96df55dad6

Tx prefix hash: 88bebba0387747b4909eea17c2240ebf0c5d1ca86d6b6568f1ae6cd35a0e23f7
Tx public key: 68ddf3ca7448293a3c22885df94d0aa5f4ea56cd43845397c375c1b0d7ad4560
Timestamp: 1704975716 Timestamp [UCT]: 2024-01-11 12:21:56 Age [y:d:h:m:s]: 01:301:22:07:44
Block: 932980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474607 RingCT/type: yes/0
Extra: 0168ddf3ca7448293a3c22885df94d0aa5f4ea56cd43845397c375c1b0d7ad45600211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2632a2a67ac50868ffd27b1300f8410a4d85ff7af06c520a4b2b0d5fb720e28c 0.600000000000 1390922 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": 932990, "vin": [ { "gen": { "height": 932980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2632a2a67ac50868ffd27b1300f8410a4d85ff7af06c520a4b2b0d5fb720e28c" } } ], "extra": [ 1, 104, 221, 243, 202, 116, 72, 41, 58, 60, 34, 136, 93, 249, 77, 10, 165, 244, 234, 86, 205, 67, 132, 83, 151, 195, 117, 193, 176, 215, 173, 69, 96, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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