Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff6b479d2bf6fb3bcf43cf89f9079bacda64759bdaed5529858a01a5d6083ce

Tx prefix hash: 1eb9f0ca669dee3abf354aea6dd5480330d83569c25f6d309cf7b013c670a931
Tx public key: f6307a973353e9909986eefc7f716aacc2f88554f8548f0d2b2c2082bdc13bfb
Timestamp: 1771615811 Timestamp [UTC]: 2026-02-20 19:30:11 Age [y:d:h:m:s]: 00:270:21:13:48
Block: 1482127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199126 RingCT/type: yes/0
Extra: 01f6307a973353e9909986eefc7f716aacc2f88554f8548f0d2b2c2082bdc13bfb021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 78e2c6769170f70e3547bed0554c10306ea09a3869e9486a154ec5695b2d81d4 0.000600000000 1971515 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": 1482137, "vin": [ { "gen": { "height": 1482127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78e2c6769170f70e3547bed0554c10306ea09a3869e9486a154ec5695b2d81d4" } } ], "extra": [ 1, 246, 48, 122, 151, 51, 83, 233, 144, 153, 134, 238, 252, 127, 113, 106, 172, 194, 248, 133, 84, 248, 84, 143, 13, 43, 44, 32, 130, 189, 193, 59, 251, 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: