Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 450f52fb567aaf6bb6567eaac47119a4f5728f62bda5df5104dd26155d178073

Tx prefix hash: 0a1bb7039390d2491078b8a16af76a241723ed2fd29d19e61a570092ea20d00f
Tx public key: 466e6dfd5e2441aa2274a8813916f287d24bac2ff870d3deefe65df60a50283d
Timestamp: 1578650130 Timestamp [UCT]: 2020-01-10 09:55:30 Age [y:d:h:m:s]: 05:006:12:18:50
Block: 42469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154989 RingCT/type: yes/0
Extra: 01466e6dfd5e2441aa2274a8813916f287d24bac2ff870d3deefe65df60a50283d0211000000094ac5aa02000000000000000000

1 output(s) for total of 443.908084061000 dcy

stealth address amount amount idx
00: cc925448a27ea7e89174145364fa98a1a7520e1ed49efb6576439e018a3e3906 443.908084061000 76542 of 0

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": 42479, "vin": [ { "gen": { "height": 42469 } } ], "vout": [ { "amount": 443908084061, "target": { "key": "cc925448a27ea7e89174145364fa98a1a7520e1ed49efb6576439e018a3e3906" } } ], "extra": [ 1, 70, 110, 109, 253, 94, 36, 65, 170, 34, 116, 168, 129, 57, 22, 242, 135, 210, 75, 172, 47, 248, 112, 211, 222, 239, 230, 93, 246, 10, 80, 40, 61, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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