Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a62d4980aa09d5dd717bca1e65496159600f37df4ae1fa0618bd28c0def11a

Tx prefix hash: 338c81bb0b75f77b85c8300db14c2daaf3d77a6106003d49400f2e67d70f5c58
Tx public key: 84e908d2af190f6cebf6ce9a4d289703cdf99db93b8ae8418825a722d450598c
Timestamp: 1714056725 Timestamp [UCT]: 2024-04-25 14:52:05 Age [y:d:h:m:s]: 00:259:12:52:12
Block: 1008284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185758 RingCT/type: yes/0
Extra: 0184e908d2af190f6cebf6ce9a4d289703cdf99db93b8ae8418825a722d450598c02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1bf8c0b78ff87982b11a2c8c716df20ccde93eb7afc0e0e3f7e34064fe88043 0.600000000000 1469752 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": 1008294, "vin": [ { "gen": { "height": 1008284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1bf8c0b78ff87982b11a2c8c716df20ccde93eb7afc0e0e3f7e34064fe88043" } } ], "extra": [ 1, 132, 233, 8, 210, 175, 25, 15, 108, 235, 246, 206, 154, 77, 40, 151, 3, 205, 249, 157, 185, 59, 138, 232, 65, 136, 37, 167, 34, 212, 80, 89, 140, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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