Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93f9a6ff3fc70b48623f27f436eedfa710f00976392d4e69106ef487d3124e0f

Tx prefix hash: 7f5d7441e76c81e67f306a4d70d0509037b51bd1d8ffc38c9b0e7eb3db8f906d
Tx public key: 6ad6e3063f676499daecefad4f7a1645b25e24f1bd31ae2bcf876dcc9d836aea
Timestamp: 1771641206 Timestamp [UTC]: 2026-02-21 02:33:26 Age [y:d:h:m:s]: 00:267:20:51:39
Block: 1482340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196898 RingCT/type: yes/0
Extra: 016ad6e3063f676499daecefad4f7a1645b25e24f1bd31ae2bcf876dcc9d836aea021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: db1fde2e134a2f9bf9995516378f3fee80d1bdadfbb7a0e9d6ca584638de804b 0.000600000000 1971732 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": 1482350, "vin": [ { "gen": { "height": 1482340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db1fde2e134a2f9bf9995516378f3fee80d1bdadfbb7a0e9d6ca584638de804b" } } ], "extra": [ 1, 106, 214, 227, 6, 63, 103, 100, 153, 218, 236, 239, 173, 79, 122, 22, 69, 178, 94, 36, 241, 189, 49, 174, 43, 207, 135, 109, 204, 157, 131, 106, 234, 2, 17, 0, 0, 0, 8, 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: