Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b540d454924548e41ff1483b344d921f22ca7c3b75a08cc8729542f0777cf84

Tx prefix hash: 0eb3bc88181f78b7e52390f6ad1e291ec7f9753a43c13e3e6a635a5a5953f7c7
Tx public key: 009eba7631417ae5f58747643530057ea8b5e3b4bb1289db3ffaa1cf66ce6c6d
Timestamp: 1702394780 Timestamp [UCT]: 2023-12-12 15:26:20 Age [y:d:h:m:s]: 01:136:20:04:14
Block: 911615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358939 RingCT/type: yes/0
Extra: 01009eba7631417ae5f58747643530057ea8b5e3b4bb1289db3ffaa1cf66ce6c6d02110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe7a3dad9de4e0d988dba865d5479e9107a8e0e8c13b1ebf60baa95d527a7c16 0.600000000000 1368829 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": 911625, "vin": [ { "gen": { "height": 911615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe7a3dad9de4e0d988dba865d5479e9107a8e0e8c13b1ebf60baa95d527a7c16" } } ], "extra": [ 1, 0, 158, 186, 118, 49, 65, 122, 229, 245, 135, 71, 100, 53, 48, 5, 126, 168, 181, 227, 180, 187, 18, 137, 219, 63, 250, 161, 207, 102, 206, 108, 109, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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