Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3776dc663ee3cf4066c659478818e87e3eed75ba9c9e367ff8e737ae4b508cc6

Tx prefix hash: 5437c0b12917797f3e93295d4231709bc23028b979af5b0c0cd7486fcd1ae42f
Tx public key: eec9bcbfe8a2dc5b888421dfd5addce78d019ff27199a00397e23a4fef36b539
Timestamp: 1747972891 Timestamp [UCT]: 2025-05-23 04:01:31 Age [y:d:h:m:s]: 00:171:17:32:51
Block: 1288928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120423 RingCT/type: yes/0
Extra: 01eec9bcbfe8a2dc5b888421dfd5addce78d019ff27199a00397e23a4fef36b5390211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8531c67b758a795e946ede78d7e11da3dca2b159b39f9be4351beed00fcd95a 0.600000000000 1776395 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": 1288938, "vin": [ { "gen": { "height": 1288928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8531c67b758a795e946ede78d7e11da3dca2b159b39f9be4351beed00fcd95a" } } ], "extra": [ 1, 238, 201, 188, 191, 232, 162, 220, 91, 136, 132, 33, 223, 213, 173, 220, 231, 141, 1, 159, 242, 113, 153, 160, 3, 151, 226, 58, 79, 239, 54, 181, 57, 2, 17, 0, 0, 0, 3, 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