Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0c45466093341617f77ba069546887eec24fa15d76dd9697580479cc40f265

Tx prefix hash: ac455c01e83a730de5185c43fb9aa73ae3225095b9622d44cb954a9ebf0c678a
Tx public key: 89068e4735bb500ebaae3b2f448fe298d95f5e9ccbccc56a6786f115c9a4550f
Timestamp: 1701163221 Timestamp [UCT]: 2023-11-28 09:20:21 Age [y:d:h:m:s]: 01:134:13:45:43
Block: 901386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357344 RingCT/type: yes/0
Extra: 0189068e4735bb500ebaae3b2f448fe298d95f5e9ccbccc56a6786f115c9a4550f02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.632898374000 dcy

stealth address amount amount idx
00: 5cd0686f18cf0007ded3bb7b530353da269efcf0f431c5f543f80d5547c69068 0.632898374000 1357945 of 0

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": 901396, "vin": [ { "gen": { "height": 901386 } } ], "vout": [ { "amount": 632898374, "target": { "key": "5cd0686f18cf0007ded3bb7b530353da269efcf0f431c5f543f80d5547c69068" } } ], "extra": [ 1, 137, 6, 142, 71, 53, 187, 80, 14, 186, 174, 59, 47, 68, 143, 226, 152, 217, 95, 94, 156, 203, 204, 197, 106, 103, 134, 241, 21, 201, 164, 85, 15, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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