Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfe6a274391f197d854a1b6cd1f01931f7cfb3394f2b97f387831f7e9d1b783d

Tx prefix hash: 1acad9235f6a99675be243e5fe212b5e645b1e0ead0a90072becaf650e4bd5cf
Tx public key: 7b6716489d1b1a26f9ebe5107a401c14ee933847c16c0317c8327c3d606ad4eb
Timestamp: 1747469029 Timestamp [UTC]: 2025-05-17 08:03:49 Age [y:d:h:m:s]: 00:359:09:07:05
Block: 1284754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246775 RingCT/type: yes/0
Extra: 017b6716489d1b1a26f9ebe5107a401c14ee933847c16c0317c8327c3d606ad4eb0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ece480d6f492f80303410e2d3b386826b1b9e0cd50d892ebe39993b5a0a7783f 0.000600000000 1772217 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": 1284764, "vin": [ { "gen": { "height": 1284754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ece480d6f492f80303410e2d3b386826b1b9e0cd50d892ebe39993b5a0a7783f" } } ], "extra": [ 1, 123, 103, 22, 72, 157, 27, 26, 38, 249, 235, 229, 16, 122, 64, 28, 20, 238, 147, 56, 71, 193, 108, 3, 23, 200, 50, 124, 61, 96, 106, 212, 235, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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: