Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411d0aa7830a315cffdb062a8444df4f2a625a1f639f41260819e634c0b719ed

Tx prefix hash: 5ed6ef31eb1d4a003d59ea4b69b45d30fc24bd87ad817b71dc995d81884698de
Tx public key: d9ee6f4e71742de5c03dc2d8ccd9ee41b78bdee2cda5ef2581296b12731b7646
Timestamp: 1737518213 Timestamp [UCT]: 2025-01-22 03:56:53 Age [y:d:h:m:s]: 00:333:02:02:45
Block: 1202598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235650 RingCT/type: yes/0
Extra: 01d9ee6f4e71742de5c03dc2d8ccd9ee41b78bdee2cda5ef2581296b12731b76460211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e63e7865a51bfe5e1d96dd339770cef133a4ff1494f424629297ff803685b8 0.600000000000 1689263 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": 1202608, "vin": [ { "gen": { "height": 1202598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e63e7865a51bfe5e1d96dd339770cef133a4ff1494f424629297ff803685b8" } } ], "extra": [ 1, 217, 238, 111, 78, 113, 116, 45, 229, 192, 61, 194, 216, 204, 217, 238, 65, 183, 139, 222, 226, 205, 165, 239, 37, 129, 41, 107, 18, 115, 27, 118, 70, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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