Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e2eb010c1878f00bf0f888141de43434cb793dabb64d923695295fcfe777978

Tx prefix hash: 1c6564ed32bfb42727e1284942195e8afc530904fb837fca9d755de22e7a0209
Tx public key: 4f0f2ba512656df5f211ba566b13d7f59d4a7b814c9138fd43b7150189513aab
Timestamp: 1695637503 Timestamp [UCT]: 2023-09-25 10:25:03 Age [y:d:h:m:s]: 01:206:08:14:44
Block: 855773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408553 RingCT/type: yes/0
Extra: 014f0f2ba512656df5f211ba566b13d7f59d4a7b814c9138fd43b7150189513aab02110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.896331896000 dcy

stealth address amount amount idx
00: 353f33657e22ea117bdc8acf9a8fa6dcd81b2b8b691c57102edc755c3865154f 0.896331896000 1309811 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": 855783, "vin": [ { "gen": { "height": 855773 } } ], "vout": [ { "amount": 896331896, "target": { "key": "353f33657e22ea117bdc8acf9a8fa6dcd81b2b8b691c57102edc755c3865154f" } } ], "extra": [ 1, 79, 15, 43, 165, 18, 101, 109, 245, 242, 17, 186, 86, 107, 19, 215, 245, 157, 74, 123, 129, 76, 145, 56, 253, 67, 183, 21, 1, 137, 81, 58, 171, 2, 17, 0, 0, 0, 12, 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