Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea8935ff5bb0cb87bd4c9b6e6332bc345d9adb1c9bb0ed044dac275b4c40bb6

Tx prefix hash: a4c51b69ef30f0d74d7a79ec5002c2ad53ff257a92f28b5649ea30fe20216825
Tx public key: 19b590b028c175a07b531a9500fc6438040f3ad3f38e51164f44cc77978f36db
Timestamp: 1705550153 Timestamp [UTC]: 2024-01-18 03:55:53 Age [y:d:h:m:s]: 02:308:14:42:30
Block: 937730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745764 RingCT/type: yes/0
Extra: 0119b590b028c175a07b531a9500fc6438040f3ad3f38e51164f44cc77978f36db02110000000259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1f9772644b4759fe01429d274457bfa9c7843001bf776abb0a3f69703843cb9 0.000600000000 1395792 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": 937740, "vin": [ { "gen": { "height": 937730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1f9772644b4759fe01429d274457bfa9c7843001bf776abb0a3f69703843cb9" } } ], "extra": [ 1, 25, 181, 144, 176, 40, 193, 117, 160, 123, 83, 26, 149, 0, 252, 100, 56, 4, 15, 58, 211, 243, 142, 81, 22, 79, 68, 204, 119, 151, 143, 54, 219, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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: