Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b71fba63aedff16032cb71c5256618cfaefa28b7d047a75735989ff2bd7a1003

Tx prefix hash: e04bf7af319fae6b1428122135f128a8341afdbcdb18d7453414011fffee846c
Tx public key: 64ffde3ba99cfaa48ce7306206f61d8754a645ad9cb2573aa4d6ce127c3ab5d3
Timestamp: 1739062503 Timestamp [UTC]: 2025-02-09 00:55:03 Age [y:d:h:m:s]: 01:090:23:01:40
Block: 1215164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316269 RingCT/type: yes/0
Extra: 0164ffde3ba99cfaa48ce7306206f61d8754a645ad9cb2573aa4d6ce127c3ab5d3021100000008007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 097f1b94d3b5b75caf92b76d19f33e1e3b382004d2dad726ebfd49d2bff86aeb 0.000600000000 1701961 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": 1215174, "vin": [ { "gen": { "height": 1215164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "097f1b94d3b5b75caf92b76d19f33e1e3b382004d2dad726ebfd49d2bff86aeb" } } ], "extra": [ 1, 100, 255, 222, 59, 169, 156, 250, 164, 140, 231, 48, 98, 6, 246, 29, 135, 84, 166, 69, 173, 156, 178, 87, 58, 164, 214, 206, 18, 124, 58, 181, 211, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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: