Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9647a0b579ca72a11abbc76b303f797babaad01979b8202dfdfdd346544f8511

Tx prefix hash: b6b73ed93f5b1d8b964c118c0c12ec23cf5bdafb07865ea65f8363acd4863d32
Tx public key: 99d55065b99f3a1eaa1b41f069acee7cf073b8def8655a2985ceb05a559ae57c
Timestamp: 1731231639 Timestamp [UCT]: 2024-11-10 09:40:39 Age [y:d:h:m:s]: 00:141:00:40:44
Block: 1150582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100612 RingCT/type: yes/0
Extra: 0199d55065b99f3a1eaa1b41f069acee7cf073b8def8655a2985ceb05a559ae57c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42a57293568a37cb5e48cab570a110c0340e8d536a58454dcce99a2defa84c39 0.600000000000 1635935 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": 1150592, "vin": [ { "gen": { "height": 1150582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42a57293568a37cb5e48cab570a110c0340e8d536a58454dcce99a2defa84c39" } } ], "extra": [ 1, 153, 213, 80, 101, 185, 159, 58, 30, 170, 27, 65, 240, 105, 172, 238, 124, 240, 115, 184, 222, 248, 101, 90, 41, 133, 206, 176, 90, 85, 154, 229, 124, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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