Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5da599fa96e86dc558531b9fad5516e86fbd603befd19afed6674b486b096d1

Tx prefix hash: 9ffec299a9a49ae3fc339e54892219023790c0f04df13111c61b0ac5d6f73100
Tx public key: 0795cb34b574a8ba813f904f4057d6938b2c0bbd1a813dd10a414b7dd3af47e1
Timestamp: 1646195566 Timestamp [UTC]: 2022-03-02 04:32:46 Age [y:d:h:m:s]: 04:260:02:32:37
Block: 449526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1229953 RingCT/type: yes/0
Extra: 010795cb34b574a8ba813f904f4057d6938b2c0bbd1a813dd10a414b7dd3af47e1021100000003d3fcec30000000000000000000

1 output(s) for total of 0.019885386400 xmr

stealth address amount amount idx tag
00: dfeefc4aeeb467d3c52f5a19fb98dfa04a074dc733dde6a6fbc0980d9185272f 0.019885386400 864163 of 0 -

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": 449536, "vin": [ { "gen": { "height": 449526 } } ], "vout": [ { "amount": 19885386400, "target": { "key": "dfeefc4aeeb467d3c52f5a19fb98dfa04a074dc733dde6a6fbc0980d9185272f" } } ], "extra": [ 1, 7, 149, 203, 52, 181, 116, 168, 186, 129, 63, 144, 79, 64, 87, 214, 147, 139, 44, 11, 189, 26, 129, 61, 209, 10, 65, 75, 125, 211, 175, 71, 225, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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: