Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976cbe804506dec217f2d67f6938737109c4d2d641f51be9a8981e680b034b52

Tx prefix hash: d47287ea7bcb8eded57ea9715d7ba0fceabaca6bde9d10f7d4fff21e8d396c25
Tx public key: 8e2adb65f6af3533a2089c04b1df18aa04d6ad30e7ccdfbff0b065dcaa98e605
Timestamp: 1706358447 Timestamp [UCT]: 2024-01-27 12:27:27 Age [y:d:h:m:s]: 01:058:23:04:32
Block: 944437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303203 RingCT/type: yes/0
Extra: 018e2adb65f6af3533a2089c04b1df18aa04d6ad30e7ccdfbff0b065dcaa98e60502110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b231aa76c01dc72e1945354fd55f7601011d700625c0f5fd0b5c0466f8b776 0.600000000000 1402673 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": 944447, "vin": [ { "gen": { "height": 944437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b231aa76c01dc72e1945354fd55f7601011d700625c0f5fd0b5c0466f8b776" } } ], "extra": [ 1, 142, 42, 219, 101, 246, 175, 53, 51, 162, 8, 156, 4, 177, 223, 24, 170, 4, 214, 173, 48, 231, 204, 223, 191, 240, 176, 101, 220, 170, 152, 230, 5, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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