Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38e28adb1acac9c62f17b0bc6c10d6e7bb5c3bcd05d288310c2a894cc6053c6

Tx prefix hash: 4002c200721facc2fde840e0e3523f6e547db893c934f2076936c39954be61ff
Tx public key: 26efe594fbbe110c067d23bcc5b859729d52f1d49ab49d6cce1198cc9934c36d
Timestamp: 1755161212 Timestamp [UCT]: 2025-08-14 08:46:52 Age [y:d:h:m:s]: 00:066:20:38:35
Block: 1346565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47284 RingCT/type: yes/0
Extra: 0126efe594fbbe110c067d23bcc5b859729d52f1d49ab49d6cce1198cc9934c36d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e06d5977a0a1067599d45a8ba9b4db9b4a796cac2bd49a2167223f2363f407a2 0.600000000000 1834466 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": 1346575, "vin": [ { "gen": { "height": 1346565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e06d5977a0a1067599d45a8ba9b4db9b4a796cac2bd49a2167223f2363f407a2" } } ], "extra": [ 1, 38, 239, 229, 148, 251, 190, 17, 12, 6, 125, 35, 188, 197, 184, 89, 114, 157, 82, 241, 212, 154, 180, 157, 108, 206, 17, 152, 204, 153, 52, 195, 109, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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