Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 740c40610d0cf7e800d3474c70f2ae0bffae512899734b51bdc11dca31d904bf

Tx prefix hash: fa6659640c56c4aec3d6f5699461352c5cdb03a249bdeb72f6159442d2ea2e38
Tx public key: 6e0740f51f5551da386aedbc36cd37c679c5c1b6daf4f66cdef9e8bf7c81a103
Timestamp: 1750367265 Timestamp [UCT]: 2025-06-19 21:07:45 Age [y:d:h:m:s]: 00:154:06:02:08
Block: 1308606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108056 RingCT/type: yes/0
Extra: 016e0740f51f5551da386aedbc36cd37c679c5c1b6daf4f66cdef9e8bf7c81a103021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e918a8323b0bfca6297a17b942b2aeb16a09a9a00ebe42fdf384ae1d129c1d7d 0.600000000000 1796219 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": 1308616, "vin": [ { "gen": { "height": 1308606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e918a8323b0bfca6297a17b942b2aeb16a09a9a00ebe42fdf384ae1d129c1d7d" } } ], "extra": [ 1, 110, 7, 64, 245, 31, 85, 81, 218, 56, 106, 237, 188, 54, 205, 55, 198, 121, 197, 193, 182, 218, 244, 246, 108, 222, 249, 232, 191, 124, 129, 161, 3, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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