Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc097332b5fcd27924f6cca7a21bece3bce33314da1f2d5bb9135db5d638e57a

Tx prefix hash: b6a1b739cd968636a1ffc9cbd0a2c4d27550b0e610c2a9881e0feb8e1c4446a5
Tx public key: 19ab03681ab9784add07a12cac79707f571ab40f1442d78e30ecfbaf7ce91a3c
Timestamp: 1706042750 Timestamp [UCT]: 2024-01-23 20:45:50 Age [y:d:h:m:s]: 01:083:02:55:26
Block: 941816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320509 RingCT/type: yes/0
Extra: 0119ab03681ab9784add07a12cac79707f571ab40f1442d78e30ecfbaf7ce91a3c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d968e4ba924e61e63303fb4b296cad8f4cf616bb603c61f529dd560b15dcb43d 0.600000000000 1399972 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": 941826, "vin": [ { "gen": { "height": 941816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d968e4ba924e61e63303fb4b296cad8f4cf616bb603c61f529dd560b15dcb43d" } } ], "extra": [ 1, 25, 171, 3, 104, 26, 185, 120, 74, 221, 7, 161, 44, 172, 121, 112, 127, 87, 26, 180, 15, 20, 66, 215, 142, 48, 236, 251, 175, 124, 233, 26, 60, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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