Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f445c005bf4b82410eaaa920c97a8b251c605333cf7882551cc572e21b0edf

Tx prefix hash: 0a92a795aee949079e1c2cf534c3a37a42e71d84d638167a8fedce9da1e83222
Tx public key: 3fae812ae8f7899d918a0f0460d6df15ded479f1ba596d021678f250f5ce0d0e
Timestamp: 1574623071 Timestamp [UCT]: 2019-11-24 19:17:51 Age [y:d:h:m:s]: 05:346:05:08:59
Block: 16642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1387776 RingCT/type: yes/0
Extra: 013fae812ae8f7899d918a0f0460d6df15ded479f1ba596d021678f250f5ce0d0e021100000001f95225a5000000000000000000

1 output(s) for total of 540.578821726000 dcy

stealth address amount amount idx
00: 4d6cac2d72723fd6c18cd39da801599786e452696ffecffec795daf3b5635736 540.578821726000 23443 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": 16652, "vin": [ { "gen": { "height": 16642 } } ], "vout": [ { "amount": 540578821726, "target": { "key": "4d6cac2d72723fd6c18cd39da801599786e452696ffecffec795daf3b5635736" } } ], "extra": [ 1, 63, 174, 129, 42, 232, 247, 137, 157, 145, 138, 15, 4, 96, 214, 223, 21, 222, 212, 121, 241, 186, 89, 109, 2, 22, 120, 242, 80, 245, 206, 13, 14, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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