Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcff5107f77e206328d319643140a538aa1f9d5fff6d184e4789ea4b08feb82c

Tx prefix hash: 9f64bff2f533d7004d998614c67ddc595e80e9828150158271ade5b333e239ba
Tx public key: 99a9498cd8aee1054f96833b20da7bb234b9e40b27a47574f81bc6e8ccfc252a
Timestamp: 1747818274 Timestamp [UTC]: 2025-05-21 09:04:34 Age [y:d:h:m:s]: 01:185:13:21:56
Block: 1287654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396496 RingCT/type: yes/0
Extra: 0199a9498cd8aee1054f96833b20da7bb234b9e40b27a47574f81bc6e8ccfc252a0211000000051f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e40430b46c993165ada195ee0edb81281d48b54e0ecc7644e5c7f3bcf3b8052 0.000600000000 1775121 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 dinastycoin-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": 1287664, "vin": [ { "gen": { "height": 1287654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e40430b46c993165ada195ee0edb81281d48b54e0ecc7644e5c7f3bcf3b8052" } } ], "extra": [ 1, 153, 169, 73, 140, 216, 174, 225, 5, 79, 150, 131, 59, 32, 218, 123, 178, 52, 185, 228, 11, 39, 164, 117, 116, 248, 27, 198, 232, 204, 252, 37, 42, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: