Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1240f762fa2c49aec28965fcbbec3389b92bac4c37332001ad995109b10cf49f

Tx prefix hash: 9c4d294d05643442fbc9e611018ab7958d0224aad4b4fc438b551a61c5079c30
Tx public key: 61ad5df61082e85b0e9ee050de8e1468e44c1b5b75409f5dc22ab463c01a689b
Timestamp: 1771072496 Timestamp [UTC]: 2026-02-14 12:34:56 Age [y:d:h:m:s]: 00:093:19:40:50
Block: 1477624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60497 RingCT/type: yes/0
Extra: 0161ad5df61082e85b0e9ee050de8e1468e44c1b5b75409f5dc22ab463c01a689b021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ef76e03828475808c12331c0164d2d5b7d14fcb8629ae22e75232287c8da65f2 0.000600000000 1966942 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": 1477634, "vin": [ { "gen": { "height": 1477624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef76e03828475808c12331c0164d2d5b7d14fcb8629ae22e75232287c8da65f2" } } ], "extra": [ 1, 97, 173, 93, 246, 16, 130, 232, 91, 14, 158, 224, 80, 222, 142, 20, 104, 228, 76, 27, 91, 117, 64, 159, 93, 194, 42, 180, 99, 192, 26, 104, 155, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: