Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f9cc05e513b96382cfa50d1ebd3d768762f523700b5271a42c3a1c5a8571700

Tx prefix hash: 242b1659438fcee5c759d377416d3749c4dbab34013903582a09c271779a6c12
Tx public key: 5c37568343c299ab0fae6ae2fa84315414a3d1c7f964c7581888476e9976b95b
Timestamp: 1580263709 Timestamp [UCT]: 2020-01-29 02:08:29 Age [y:d:h:m:s]: 04:352:05:39:57
Block: 54314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142711 RingCT/type: yes/0
Extra: 015c37568343c299ab0fae6ae2fa84315414a3d1c7f964c7581888476e9976b95b021100000002dcee4b4d000000000000000000

1 output(s) for total of 405.573328676000 dcy

stealth address amount amount idx
00: 36e56c4dba67fc6e04b37ea65d3379208418f1a013c60f22647ced193879ec15 405.573328676000 100661 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": 54324, "vin": [ { "gen": { "height": 54314 } } ], "vout": [ { "amount": 405573328676, "target": { "key": "36e56c4dba67fc6e04b37ea65d3379208418f1a013c60f22647ced193879ec15" } } ], "extra": [ 1, 92, 55, 86, 131, 67, 194, 153, 171, 15, 174, 106, 226, 250, 132, 49, 84, 20, 163, 209, 199, 249, 100, 199, 88, 24, 136, 71, 110, 153, 118, 185, 91, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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