Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52ebb9feb0fa7f5d1b1bfdea60ad6defc21e711afadaffb3c0890f68db09a091

Tx prefix hash: c9b8c2de04b2a007c0e3c314dec46b2cc4026a701219fbf2bc5506a1c4cd916d
Tx public key: d5d675a25f4636f45cafac6608f4186066451336ba8ba1fa53313c72f99cedf6
Timestamp: 1710143705 Timestamp [UCT]: 2024-03-11 07:55:05 Age [y:d:h:m:s]: 01:025:14:55:36
Block: 975855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279289 RingCT/type: yes/0
Extra: 01d5d675a25f4636f45cafac6608f4186066451336ba8ba1fa53313c72f99cedf6021100000005f42f4dfc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eea0659d0d98a1a0e905319a3282d502e48cedc6f95700a7b45eda6b249657e4 0.600000000000 1435832 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": 975865, "vin": [ { "gen": { "height": 975855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eea0659d0d98a1a0e905319a3282d502e48cedc6f95700a7b45eda6b249657e4" } } ], "extra": [ 1, 213, 214, 117, 162, 95, 70, 54, 244, 92, 175, 172, 102, 8, 244, 24, 96, 102, 69, 19, 54, 186, 139, 161, 250, 83, 49, 60, 114, 249, 156, 237, 246, 2, 17, 0, 0, 0, 5, 244, 47, 77, 252, 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