Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf23c49795e2bf890eb84e3735d62b8e9fd5a313f5cb8f39ddbd672a0124f18f

Tx prefix hash: d7c3f2608a9907157823cb3138b027b938323fff86b016a78ff2eeb216bca9da
Tx public key: 34c5ed3904fd8d5c112a11a5e4da4a432be39b4beedf00a298368f1a8a05e27c
Timestamp: 1760669466 Timestamp [UTC]: 2025-10-17 02:51:06 Age [y:d:h:m:s]: 01:028:19:10:57
Block: 1391614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286816 RingCT/type: yes/0
Extra: 0134c5ed3904fd8d5c112a11a5e4da4a432be39b4beedf00a298368f1a8a05e27c0211000000052609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d8c5a4526949026b2484360cfd2b6729a94c15f841834ebd1aa4563cf6fb15e1 0.000600000000 1879861 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": 1391624, "vin": [ { "gen": { "height": 1391614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8c5a4526949026b2484360cfd2b6729a94c15f841834ebd1aa4563cf6fb15e1" } } ], "extra": [ 1, 52, 197, 237, 57, 4, 253, 141, 92, 17, 42, 17, 165, 228, 218, 74, 67, 43, 227, 155, 75, 238, 223, 0, 162, 152, 54, 143, 26, 138, 5, 226, 124, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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: