Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f221c0afda5365b467150e1c2cf7a01fd55584d17298dbcdead7bd5d5be2dc8

Tx prefix hash: 2f48dccdf2e5fd8a0a6a8ebbe2bfb98dc12721c8430ffc63dce55c9ea2f24878
Tx public key: 6479f147a1e77b9a60206b83c4f80122ef86b99e7f91bafe498a56055cc56922
Timestamp: 1724920112 Timestamp [UCT]: 2024-08-29 08:28:32 Age [y:d:h:m:s]: 00:217:17:28:45
Block: 1098341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155457 RingCT/type: yes/0
Extra: 016479f147a1e77b9a60206b83c4f80122ef86b99e7f91bafe498a56055cc5692202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64d28a591578200f5848e80c2fbd9676d1aa062c3b2b3539f654c86fdab20486 0.600000000000 1574026 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": 1098351, "vin": [ { "gen": { "height": 1098341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64d28a591578200f5848e80c2fbd9676d1aa062c3b2b3539f654c86fdab20486" } } ], "extra": [ 1, 100, 121, 241, 71, 161, 231, 123, 154, 96, 32, 107, 131, 196, 248, 1, 34, 239, 134, 185, 158, 127, 145, 186, 254, 73, 138, 86, 5, 92, 197, 105, 34, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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