Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5bd87a458687f084e2a261debe5743cc8bba013a377b331d98e5ffc46ed55b

Tx prefix hash: 0ef4cf6f363f9cbab5f025b084e68f9fad38264bac9748e2a324bd972601c7c7
Tx public key: 0382020a86a2c676e269233a7125d04be9d8832c22485559e3e5dbf629c158e8
Timestamp: 1772005059 Timestamp [UTC]: 2026-02-25 07:37:39 Age [y:d:h:m:s]: 00:266:23:29:45
Block: 1485381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196333 RingCT/type: yes/0
Extra: 010382020a86a2c676e269233a7125d04be9d8832c22485559e3e5dbf629c158e8021100000018f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 553639ad9b69586d6876e90b9e6c0090a0e655634cff24722bb341ef52f4edcd 0.000600000000 1974815 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": 1485391, "vin": [ { "gen": { "height": 1485381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553639ad9b69586d6876e90b9e6c0090a0e655634cff24722bb341ef52f4edcd" } } ], "extra": [ 1, 3, 130, 2, 10, 134, 162, 198, 118, 226, 105, 35, 58, 113, 37, 208, 75, 233, 216, 131, 44, 34, 72, 85, 89, 227, 229, 219, 246, 41, 193, 88, 232, 2, 17, 0, 0, 0, 24, 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: