Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f84baefcd16adcfb503949c452a8199d17841adc61543c20fa5f87bccf4748

Tx prefix hash: 3e5ff317a41d37d0def5954bf586f139b520277da3204598a88e8c128bf3bb7a
Tx public key: 0ff6a6d13b6f97c7df37cf47a08aff2826afe0ae80161d349f0a991257ee75c0
Timestamp: 1742595141 Timestamp [UTC]: 2025-03-21 22:12:21 Age [y:d:h:m:s]: 01:244:13:37:16
Block: 1244403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438984 RingCT/type: yes/0
Extra: 010ff6a6d13b6f97c7df37cf47a08aff2826afe0ae80161d349f0a991257ee75c0021100000008af845649000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ff9962bf6819731dbc15d6a183dd102e740bbf3eab22a2a3884b00e2e36c091 0.000600000000 1731394 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": 1244413, "vin": [ { "gen": { "height": 1244403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff9962bf6819731dbc15d6a183dd102e740bbf3eab22a2a3884b00e2e36c091" } } ], "extra": [ 1, 15, 246, 166, 209, 59, 111, 151, 199, 223, 55, 207, 71, 160, 138, 255, 40, 38, 175, 224, 174, 128, 22, 29, 52, 159, 10, 153, 18, 87, 238, 117, 192, 2, 17, 0, 0, 0, 8, 175, 132, 86, 73, 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: