Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01ca60c5ccb037bf142bde6f05fda7cd6e77a837a751caeec5cc858fabeba89

Tx prefix hash: 2b048648835887d2267cb3d6643ca2fcab69f11051b84a7a467fe8e700b2f19f
Tx public key: 5ca1667474780f48d6a224c29e7d5acdae39e51e285ec5acb691d385e3f0cf2e
Timestamp: 1710979760 Timestamp [UCT]: 2024-03-21 00:09:20 Age [y:d:h:m:s]: 00:361:05:49:38
Block: 982795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258276 RingCT/type: yes/0
Extra: 015ca1667474780f48d6a224c29e7d5acdae39e51e285ec5acb691d385e3f0cf2e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9be00226f5660cc5daf7eeae61f7ff5c94d229c5820055678b2f3c6aa190bc1e 0.600000000000 1442906 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": 982805, "vin": [ { "gen": { "height": 982795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9be00226f5660cc5daf7eeae61f7ff5c94d229c5820055678b2f3c6aa190bc1e" } } ], "extra": [ 1, 92, 161, 102, 116, 116, 120, 15, 72, 214, 162, 36, 194, 158, 125, 90, 205, 174, 57, 229, 30, 40, 94, 197, 172, 182, 145, 211, 133, 227, 240, 207, 46, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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