Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a896b1e44d441c5131bc7bcbd9ea05d2d678ccb66ef9671da603e01489d75a59

Tx prefix hash: ded6ddb5fd7babe19cf17f03df06060834743f2cc93b79ab58430b0db3710fb6
Tx public key: f9e9fad43ed0763bddf6f64e40d5d566089405835823d99dedbf4d6bb5c1e82c
Timestamp: 1772033403 Timestamp [UTC]: 2026-02-25 15:30:03 Age [y:d:h:m:s]: 00:267:20:51:27
Block: 1485614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197062 RingCT/type: yes/0
Extra: 01f9e9fad43ed0763bddf6f64e40d5d566089405835823d99dedbf4d6bb5c1e82c021100000016e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 92e5bb6942ac3787eddfc1b5c89dc23cd440eed8fe63dec90ae798fdec2c8ddf 0.000600000000 1975052 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": 1485624, "vin": [ { "gen": { "height": 1485614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92e5bb6942ac3787eddfc1b5c89dc23cd440eed8fe63dec90ae798fdec2c8ddf" } } ], "extra": [ 1, 249, 233, 250, 212, 62, 208, 118, 59, 221, 246, 246, 78, 64, 213, 213, 102, 8, 148, 5, 131, 88, 35, 217, 157, 237, 191, 77, 107, 181, 193, 232, 44, 2, 17, 0, 0, 0, 22, 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: