Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6805a7dcd07b903320aeee243eeb9def8b9ab44752ab0f53ee2fbed089f5b5c

Tx prefix hash: 32ad247da45fb311b1d29c692a5ce7d2fbf9780d540c4d02f65225c3688aaae3
Tx public key: 394a8ac6a8251e210a3b7b052858b72b200cd2b5ec1b07c2cf9549d827c5a3da
Timestamp: 1700843671 Timestamp [UCT]: 2023-11-24 16:34:31 Age [y:d:h:m:s]: 01:090:02:29:53
Block: 898745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325509 RingCT/type: yes/0
Extra: 01394a8ac6a8251e210a3b7b052858b72b200cd2b5ec1b07c2cf9549d827c5a3da02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.645780183000 dcy

stealth address amount amount idx
00: f4f31daa22bd5bfceb821ceb23f1375ea6ae496ce38e44cd5fedcc7a32063235 0.645780183000 1355178 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": 898755, "vin": [ { "gen": { "height": 898745 } } ], "vout": [ { "amount": 645780183, "target": { "key": "f4f31daa22bd5bfceb821ceb23f1375ea6ae496ce38e44cd5fedcc7a32063235" } } ], "extra": [ 1, 57, 74, 138, 198, 168, 37, 30, 33, 10, 59, 123, 5, 40, 88, 183, 43, 32, 12, 210, 181, 236, 27, 7, 194, 207, 149, 73, 216, 39, 197, 163, 218, 2, 17, 0, 0, 0, 7, 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