Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 145cb77001b89991fb5ff6bef15c13f020ba6173d8a658d5ed0e514ed88075b0

Tx prefix hash: 6dc9eb1efbc8f184d03d14dbafa3c1dcc06b5d8d91379a873cf97d12e5f902cc
Tx public key: 95760a0ed866b9cd2b9006f772b5f832301eee4a632e2912201d6120b3d1da7d
Timestamp: 1747285701 Timestamp [UCT]: 2025-05-15 05:08:21 Age [y:d:h:m:s]: 00:189:17:18:59
Block: 1283237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133293 RingCT/type: yes/0
Extra: 0195760a0ed866b9cd2b9006f772b5f832301eee4a632e2912201d6120b3d1da7d0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa0e54be169c237d6e15e2a203906264f2fca85689c62aa2e8765d650fcffb18 0.600000000000 1770654 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": 1283247, "vin": [ { "gen": { "height": 1283237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa0e54be169c237d6e15e2a203906264f2fca85689c62aa2e8765d650fcffb18" } } ], "extra": [ 1, 149, 118, 10, 14, 216, 102, 185, 205, 43, 144, 6, 247, 114, 181, 248, 50, 48, 30, 238, 74, 99, 46, 41, 18, 32, 29, 97, 32, 179, 209, 218, 125, 2, 17, 0, 0, 0, 4, 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