Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34606282bcac16b4d24190921cc131dfb04b4865f25f7e00a48c9062c1eb3d3c

Tx prefix hash: 657ef2320dddbe4cc9b9f50e3bfdfc0dcf773143602f26921e1b2ef08ad260eb
Tx public key: d60d6f5f09aa1a32c44524f33521a2a171616c2c57e6413b269796f8855c4d6f
Timestamp: 1749503118 Timestamp [UCT]: 2025-06-09 21:05:18 Age [y:d:h:m:s]: 00:164:19:04:31
Block: 1301601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115450 RingCT/type: yes/0
Extra: 01d60d6f5f09aa1a32c44524f33521a2a171616c2c57e6413b269796f8855c4d6f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bfd84543ef3dc3a4e8a1a6f8de074a971c565e8b6945855b046c63167537951 0.600000000000 1789162 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": 1301611, "vin": [ { "gen": { "height": 1301601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bfd84543ef3dc3a4e8a1a6f8de074a971c565e8b6945855b046c63167537951" } } ], "extra": [ 1, 214, 13, 111, 95, 9, 170, 26, 50, 196, 69, 36, 243, 53, 33, 162, 161, 113, 97, 108, 44, 87, 230, 65, 59, 38, 151, 150, 248, 133, 92, 77, 111, 2, 17, 0, 0, 0, 1, 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