Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93a0a674a068d3f37664fa9e8a2e4453e2deb4cf2275838efacc252e9769bef6

Tx prefix hash: 2b998094ada36fadd1c93175b41cb4b82b9f640713ed4c02a1f52e4aaa436c8a
Tx public key: 093827e378c9932dc1ee2be8d14d0ef631a50a3d2ec454ac4d2982238b317a56
Timestamp: 1772612349 Timestamp [UTC]: 2026-03-04 08:19:09 Age [y:d:h:m:s]: 00:261:08:25:51
Block: 1490367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192465 RingCT/type: yes/0
Extra: 01093827e378c9932dc1ee2be8d14d0ef631a50a3d2ec454ac4d2982238b317a56021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 885185296d8a53eace126fa99c3364d1b38e68072a1c04d9aaef7eab8e7e2c01 0.000600000000 1979869 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": 1490377, "vin": [ { "gen": { "height": 1490367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "885185296d8a53eace126fa99c3364d1b38e68072a1c04d9aaef7eab8e7e2c01" } } ], "extra": [ 1, 9, 56, 39, 227, 120, 201, 147, 45, 193, 238, 43, 232, 209, 77, 14, 246, 49, 165, 10, 61, 46, 196, 84, 172, 77, 41, 130, 35, 139, 49, 122, 86, 2, 17, 0, 0, 0, 5, 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: