Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5fdd023f63e0ac9d025561cf5bbe321ad6314bc7e9e7821a9cb50a1aa3ee5eb

Tx prefix hash: c305f9246993e0d91f5bdd8485f04e4bd5427ac7b84be3d17971801894dc56f9
Tx public key: 00a9226267e8dee6b63da84b904d376c6399de0c51113e56008b226c2d50d53b
Timestamp: 1746479028 Timestamp [UCT]: 2025-05-05 21:03:48 Age [y:d:h:m:s]: 00:270:19:35:41
Block: 1276548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191189 RingCT/type: yes/0
Extra: 0100a9226267e8dee6b63da84b904d376c6399de0c51113e56008b226c2d50d53b0211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5c6a6462f827e4db8de4e21561730a652dee501e828cd6cd019fac68d5ba58d 0.600000000000 1763895 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": 1276558, "vin": [ { "gen": { "height": 1276548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5c6a6462f827e4db8de4e21561730a652dee501e828cd6cd019fac68d5ba58d" } } ], "extra": [ 1, 0, 169, 34, 98, 103, 232, 222, 230, 182, 61, 168, 75, 144, 77, 55, 108, 99, 153, 222, 12, 81, 17, 62, 86, 0, 139, 34, 108, 45, 80, 213, 59, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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