Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ca9e5d52c4a536a89eeb6b6151ccca0d79e74992013e05f35b49b436b417c89

Tx prefix hash: 84963ab35f1b91a346fc44375b1bf99b3ebcdeb14ba13fc69de9c2204b6c3227
Tx public key: 1036fbbcb5dae3a3935f2b00c9be066a7e8bd7b04efac98ad616e735899fdca4
Timestamp: 1736499998 Timestamp [UCT]: 2025-01-10 09:06:38 Age [y:d:h:m:s]: 00:073:08:32:49
Block: 1194204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52202 RingCT/type: yes/0
Extra: 011036fbbcb5dae3a3935f2b00c9be066a7e8bd7b04efac98ad616e735899fdca40211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30cf503ef0f46710a2c3b48abc72fb1bb97bc0028de1419e926b901b15b587b2 0.600000000000 1680771 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": 1194214, "vin": [ { "gen": { "height": 1194204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30cf503ef0f46710a2c3b48abc72fb1bb97bc0028de1419e926b901b15b587b2" } } ], "extra": [ 1, 16, 54, 251, 188, 181, 218, 227, 163, 147, 95, 43, 0, 201, 190, 6, 106, 126, 139, 215, 176, 78, 250, 201, 138, 214, 22, 231, 53, 137, 159, 220, 164, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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