Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b178413b19e3ebf76ff269672498aeeeca6398a3d03b07e1e17045b64f1bfbf9

Tx prefix hash: 590e8064415a3fbdbcb590022d46c09a2ebb046061ab9d93e7d79cf6c497bb0e
Tx public key: 72c3d4d3805f3c76266bb338c4c7f52f144d21d3a6e8c089c7945358d779b339
Timestamp: 1582132632 Timestamp [UCT]: 2020-02-19 17:17:12 Age [y:d:h:m:s]: 05:255:15:21:33
Block: 68447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1333367 RingCT/type: yes/0
Extra: 0172c3d4d3805f3c76266bb338c4c7f52f144d21d3a6e8c089c7945358d779b3390211000000010aca7173000000000000000000

1 output(s) for total of 364.088935613000 dcy

stealth address amount amount idx
00: b31dc487029cdae7bef279e56db34e28a9562c7d2b4482d85aaf7702381ba992 364.088935613000 126065 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": 68457, "vin": [ { "gen": { "height": 68447 } } ], "vout": [ { "amount": 364088935613, "target": { "key": "b31dc487029cdae7bef279e56db34e28a9562c7d2b4482d85aaf7702381ba992" } } ], "extra": [ 1, 114, 195, 212, 211, 128, 95, 60, 118, 38, 107, 179, 56, 196, 199, 245, 47, 20, 77, 33, 211, 166, 232, 192, 137, 199, 148, 83, 88, 215, 121, 179, 57, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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