Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f74e34ae0c82fbd589c5e70b2f2ba7e32bd551e38e1bf4eedde7fba4ac7c9bc

Tx prefix hash: 0799a8608f52391bbd9d83cb3b8e30e27d88a4933d59ed15eb80964da5ff95de
Tx public key: 05d401d500fc3f1ebde472ecccea05d580abc176ab4ccae87116e2300eada841
Timestamp: 1772464092 Timestamp [UTC]: 2026-03-02 15:08:12 Age [y:d:h:m:s]: 00:265:00:17:02
Block: 1489144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194350 RingCT/type: yes/0
Extra: 0105d401d500fc3f1ebde472ecccea05d580abc176ab4ccae87116e2300eada841021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0dcf90a822e9172a7e39b1e5bfeb9df0155d9fa4744cf12323da7a31f619939 0.000600000000 1978632 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": 1489154, "vin": [ { "gen": { "height": 1489144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0dcf90a822e9172a7e39b1e5bfeb9df0155d9fa4744cf12323da7a31f619939" } } ], "extra": [ 1, 5, 212, 1, 213, 0, 252, 63, 30, 189, 228, 114, 236, 204, 234, 5, 213, 128, 171, 193, 118, 171, 76, 202, 232, 113, 22, 226, 48, 14, 173, 168, 65, 2, 17, 0, 0, 0, 3, 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: