Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0075e2ffd2a0cf89eadfed2739ed166530fdf61fcbd34edd0199f8db5542034b

Tx prefix hash: 2a59155278a080eeeb05969dece8666c7b2dc5dd113d0ff71f89fa05fdd12faf
Tx public key: 8159b8abba2aa5cf5472d52450b0e974a5ce5d2f195af8674af4f28784681f39
Timestamp: 1772700478 Timestamp [UTC]: 2026-03-05 08:47:58 Age [y:d:h:m:s]: 00:255:11:27:05
Block: 1491103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188032 RingCT/type: yes/0
Extra: 018159b8abba2aa5cf5472d52450b0e974a5ce5d2f195af8674af4f28784681f39021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e4994c4e95cd6a0d9cdd491cc05708d91ba23303cb80366a59d5b5b34045a51 0.000600000000 1980617 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": 1491113, "vin": [ { "gen": { "height": 1491103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e4994c4e95cd6a0d9cdd491cc05708d91ba23303cb80366a59d5b5b34045a51" } } ], "extra": [ 1, 129, 89, 184, 171, 186, 42, 165, 207, 84, 114, 213, 36, 80, 176, 233, 116, 165, 206, 93, 47, 25, 90, 248, 103, 74, 244, 242, 135, 132, 104, 31, 57, 2, 17, 0, 0, 0, 1, 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: