Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e2ab536ab88eb5b682e462af4a28656bbbf03414486518e17285de74a786cff

Tx prefix hash: a5fe8a0b2ab3281c33d718fdc30b0ad7f976813f030c353f76861873c10f7474
Tx public key: 79ab705299a62ff603f3c93618b566941811aa3c8b96388d6fe81a7067960669
Timestamp: 1774539421 Timestamp [UTC]: 2026-03-26 15:37:01 Age [y:d:h:m:s]: 00:238:09:44:54
Block: 1506304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175992 RingCT/type: yes/0
Extra: 0179ab705299a62ff603f3c93618b566941811aa3c8b96388d6fe81a7067960669021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ffc0d7aee17424c904511c36748daaf0f09d8f23b3722ae4de4f713fb44d87c2 0.000600000000 1996048 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": 1506314, "vin": [ { "gen": { "height": 1506304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffc0d7aee17424c904511c36748daaf0f09d8f23b3722ae4de4f713fb44d87c2" } } ], "extra": [ 1, 121, 171, 112, 82, 153, 166, 47, 246, 3, 243, 201, 54, 24, 181, 102, 148, 24, 17, 170, 60, 139, 150, 56, 141, 111, 232, 26, 112, 103, 150, 6, 105, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: