Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1d5d0833d803f52249640e83c1bfd938d67e33cbd497300851a64ecf6a8b60c

Tx prefix hash: 5bbaca5ac0900ab9f19c7f36332a13ac6bd139948bd585dd96089adfefb51221
Tx public key: f742aace895f54d9f9c65d3d1f8fe2cf2477c72153f7dbc4064a49d5b640c317
Timestamp: 1714564362 Timestamp [UCT]: 2024-05-01 11:52:42 Age [y:d:h:m:s]: 00:303:13:49:25
Block: 1012494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216974 RingCT/type: yes/0
Extra: 01f742aace895f54d9f9c65d3d1f8fe2cf2477c72153f7dbc4064a49d5b640c3170211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70317c9e6f241aefaaee945bd79461d9c1824ff134db6ecdf1ea894f768058df 0.600000000000 1475040 of 15

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": 1012504, "vin": [ { "gen": { "height": 1012494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70317c9e6f241aefaaee945bd79461d9c1824ff134db6ecdf1ea894f768058df" } } ], "extra": [ 1, 247, 66, 170, 206, 137, 95, 84, 217, 249, 198, 93, 61, 31, 143, 226, 207, 36, 119, 199, 33, 83, 247, 219, 196, 6, 74, 73, 213, 182, 64, 195, 23, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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