Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353b497ee6163376885ff39bfa11c28bb197098e5a36ceb0949c1df50923b201

Tx prefix hash: f5442731a8104235176f85a266f24211633bcc438e76526fa3ac63a7559813a8
Tx public key: cde2268d1ef6873d4b50704f500c83cced38534ff8a4e2e3ca90ea6d44015df9
Timestamp: 1772829213 Timestamp [UTC]: 2026-03-06 20:33:33 Age [y:d:h:m:s]: 00:256:10:27:01
Block: 1492175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188782 RingCT/type: yes/0
Extra: 01cde2268d1ef6873d4b50704f500c83cced38534ff8a4e2e3ca90ea6d44015df902110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88764d02cbe04081094c9f8f526b9f3c29379f2708cefe5f4e4d6e57bca5daef 0.000600000000 1981713 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": 1492185, "vin": [ { "gen": { "height": 1492175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88764d02cbe04081094c9f8f526b9f3c29379f2708cefe5f4e4d6e57bca5daef" } } ], "extra": [ 1, 205, 226, 38, 141, 30, 246, 135, 61, 75, 80, 112, 79, 80, 12, 131, 204, 237, 56, 83, 79, 248, 164, 226, 227, 202, 144, 234, 109, 68, 1, 93, 249, 2, 17, 0, 0, 0, 12, 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: