Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33cd7966bb099c2279d19e19e2ebfce87c3a47f7d2d2beec46688bd3c55480e

Tx prefix hash: 8d1e634439779646ad0cb847160b0c64ac65aa2069adf53ce18e8bbfc6320ffa
Tx public key: ef6a5cf3f8051b58843c9a10c4f881fd7d0667901a149c108acd9460c4c1ac61
Timestamp: 1745801058 Timestamp [UCT]: 2025-04-28 00:44:18 Age [y:d:h:m:s]: 00:015:23:49:45
Block: 1270946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11440 RingCT/type: yes/0
Extra: 01ef6a5cf3f8051b58843c9a10c4f881fd7d0667901a149c108acd9460c4c1ac6102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0239bfa6c6554e9c2dcd21d3d5d7a329e0955313eeaa731c347033e4d995da2 0.600000000000 1758191 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": 1270956, "vin": [ { "gen": { "height": 1270946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0239bfa6c6554e9c2dcd21d3d5d7a329e0955313eeaa731c347033e4d995da2" } } ], "extra": [ 1, 239, 106, 92, 243, 248, 5, 27, 88, 132, 60, 154, 16, 196, 248, 129, 253, 125, 6, 103, 144, 26, 20, 156, 16, 138, 205, 148, 96, 196, 193, 172, 97, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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