Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 701a0b87c688ffc64e1efa32bcc08812fd0fb5af7a4a794d00e37841d078598c

Tx prefix hash: ece2347058e91839beabcebe023c48ce1d4c813523399bcda545f2c1e430e445
Tx public key: 1bc80d26a1d2a9ca037d6736819e98b53feda7af91b96f2a6d4686d6f6762f54
Timestamp: 1747390106 Timestamp [UTC]: 2025-05-16 10:08:26 Age [y:d:h:m:s]: 01:002:22:41:28
Block: 1284094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254045 RingCT/type: yes/0
Extra: 011bc80d26a1d2a9ca037d6736819e98b53feda7af91b96f2a6d4686d6f6762f540211000000049f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0e960daf8e62776df8a1071fe08c700ea25563d218cfb33adf57030529e23e70 0.000600000000 1771529 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": 1284104, "vin": [ { "gen": { "height": 1284094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e960daf8e62776df8a1071fe08c700ea25563d218cfb33adf57030529e23e70" } } ], "extra": [ 1, 27, 200, 13, 38, 161, 210, 169, 202, 3, 125, 103, 54, 129, 158, 152, 181, 63, 237, 167, 175, 145, 185, 111, 42, 109, 70, 134, 214, 246, 118, 47, 84, 2, 17, 0, 0, 0, 4, 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: