Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f53bdafc14d809a17de5a53333efdb1fd9a1e1cc08ca3c3abc4af6d203fa492

Tx prefix hash: 9e447eae59e6738367034469d8e6f00c603197281cecd1bbcdf06ba3ec30bd1d
Tx public key: f7583464ba8d567d3ad17610849a1f602f29f95f7ae95b99a87ea5bf93378fcf
Timestamp: 1700370840 Timestamp [UCT]: 2023-11-19 05:14:00 Age [y:d:h:m:s]: 01:202:01:35:58
Block: 894818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405644 RingCT/type: yes/0
Extra: 01f7583464ba8d567d3ad17610849a1f602f29f95f7ae95b99a87ea5bf93378fcf02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.665420996000 dcy

stealth address amount amount idx
00: ef8691afaef6c5815ad3420394ed39d23cb45507bb6e275e67f7dbc816be642e 0.665420996000 1351029 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": 894828, "vin": [ { "gen": { "height": 894818 } } ], "vout": [ { "amount": 665420996, "target": { "key": "ef8691afaef6c5815ad3420394ed39d23cb45507bb6e275e67f7dbc816be642e" } } ], "extra": [ 1, 247, 88, 52, 100, 186, 141, 86, 125, 58, 209, 118, 16, 132, 154, 31, 96, 47, 41, 249, 95, 122, 233, 91, 153, 168, 126, 165, 191, 147, 55, 143, 207, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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