Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3041c24a78214e5a6467ead89fb156bfb9843cb7807ff814f2d7802b667b2910

Tx prefix hash: 4a3ca9cacae01a5bff151aa3fe7d038bb39927504fe6c66ab1a2d22ff89b5690
Tx public key: 16f40134f5db0fee29800fba0c7df6d2f9805a6a85deacaea4a175fcdcf16839
Timestamp: 1763968016 Timestamp [UCT]: 2025-11-24 07:06:56 Age [y:d:h:m:s]: 00:003:10:21:30
Block: 1418936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2476 RingCT/type: yes/0
Extra: 0116f40134f5db0fee29800fba0c7df6d2f9805a6a85deacaea4a175fcdcf1683902110000000ad6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca3ec7e9e8caf9405ede0b85a8d5441424cb41d1aeb6e8faad43032bf70536e1 0.600000000000 1907469 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": 1418946, "vin": [ { "gen": { "height": 1418936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca3ec7e9e8caf9405ede0b85a8d5441424cb41d1aeb6e8faad43032bf70536e1" } } ], "extra": [ 1, 22, 244, 1, 52, 245, 219, 15, 238, 41, 128, 15, 186, 12, 125, 246, 210, 249, 128, 90, 106, 133, 222, 172, 174, 164, 161, 117, 252, 220, 241, 104, 57, 2, 17, 0, 0, 0, 10, 214, 225, 157, 124, 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