Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac88bf8c0da12c2a3efb6f7a56776d8da804c480243567cf57224d47fe2c49ed

Tx prefix hash: 2ef35a9c49438cb47f8477e705deb63b508b82808377718ac4af175b2c3ab2cd
Tx public key: 310b1886adf96dad9a5deb1311c94d23c6fdfeff699d79a0aa935893b5c59626
Timestamp: 1743016002 Timestamp [UTC]: 2025-03-26 19:06:42 Age [y:d:h:m:s]: 01:239:17:34:58
Block: 1247869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435538 RingCT/type: yes/0
Extra: 01310b1886adf96dad9a5deb1311c94d23c6fdfeff699d79a0aa935893b5c59626021100000001d2e40efd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61213d4eedb59d666800704c7b0a2854509f6afb442f28f67443ab4962670a86 0.000600000000 1734896 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": 1247879, "vin": [ { "gen": { "height": 1247869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61213d4eedb59d666800704c7b0a2854509f6afb442f28f67443ab4962670a86" } } ], "extra": [ 1, 49, 11, 24, 134, 173, 249, 109, 173, 154, 93, 235, 19, 17, 201, 77, 35, 198, 253, 254, 255, 105, 157, 121, 160, 170, 147, 88, 147, 181, 197, 150, 38, 2, 17, 0, 0, 0, 1, 210, 228, 14, 253, 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: