Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85c1dc1586fddfb57a60915705a88ea9c12775dca971d5c61dc1f6ea78fb174b

Tx prefix hash: 6f238c0d7c3b7d66a877580c174011d7ece8fa5e12f96176c68170744da250e9
Tx public key: e5d5a7745f1eb082ca5b621dafb373b90dec5c115639f94f35ee5e4316e95e2a
Timestamp: 1771322700 Timestamp [UTC]: 2026-02-17 10:05:00 Age [y:d:h:m:s]: 00:274:19:03:22
Block: 1479682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201974 RingCT/type: yes/0
Extra: 01e5d5a7745f1eb082ca5b621dafb373b90dec5c115639f94f35ee5e4316e95e2a021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f50137e4abb49d0fb61508c12859bcd3a1573d366bf71749a794a1d42e80f7c9 0.000600000000 1969036 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": 1479692, "vin": [ { "gen": { "height": 1479682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50137e4abb49d0fb61508c12859bcd3a1573d366bf71749a794a1d42e80f7c9" } } ], "extra": [ 1, 229, 213, 167, 116, 95, 30, 176, 130, 202, 91, 98, 29, 175, 179, 115, 185, 13, 236, 92, 17, 86, 57, 249, 79, 53, 238, 94, 67, 22, 233, 94, 42, 2, 17, 0, 0, 0, 1, 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: