Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c6dda827025602d5c1a46c40ab2234b2295b3d394e60641af466b0b253f809b

Tx prefix hash: 2ea612af33598b6bbaeb60f307b88342fd3ca6ac8b4d9188dc7238f9bbff0224
Tx public key: 1a67d0210997136298ead68fb2a1a6f8e4868a012bc1d72ed69ec7e649c9caeb
Timestamp: 1703755739 Timestamp [UCT]: 2023-12-28 09:28:59 Age [y:d:h:m:s]: 01:326:12:43:57
Block: 922886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492209 RingCT/type: yes/0
Extra: 011a67d0210997136298ead68fb2a1a6f8e4868a012bc1d72ed69ec7e649c9caeb021100000004ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46a430a55501f288b1329c3cc5c9e3e439ec3c4119120386e31292e34b06f5e9 0.600000000000 1380592 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": 922896, "vin": [ { "gen": { "height": 922886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46a430a55501f288b1329c3cc5c9e3e439ec3c4119120386e31292e34b06f5e9" } } ], "extra": [ 1, 26, 103, 208, 33, 9, 151, 19, 98, 152, 234, 214, 143, 178, 161, 166, 248, 228, 134, 138, 1, 43, 193, 215, 46, 214, 158, 199, 230, 73, 201, 202, 235, 2, 17, 0, 0, 0, 4, 173, 86, 148, 172, 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