Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cca3fda3e966769e52fbca7a51dc996bf3d05cf701086831d6b21cbbcfd7b7b

Tx prefix hash: edc8a8ee39e8ad48b81e78c319e00ea8aef096ba3a9da50d4edcba251b070554
Tx public key: e6fc81061991236bc1085a01103a0a9e0d4b90aafd2282e7170b4657596ebf6e
Timestamp: 1576644338 Timestamp [UTC]: 2019-12-18 04:45:38 Age [y:d:h:m:s]: 06:062:23:04:46
Block: 28563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1450935 RingCT/type: yes/0
Extra: 01e6fc81061991236bc1085a01103a0a9e0d4b90aafd2282e7170b4657596ebf6e0211000000034943cd9f000000000000000000

1 output(s) for total of 0.493582539740 xmr

stealth address amount amount idx tag
00: 9e4cf08b63f040bb0b2b7388e65c560b3be428f7d0f530a2d9949416c81b8bf1 0.493582539740 47117 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": 28573, "vin": [ { "gen": { "height": 28563 } } ], "vout": [ { "amount": 493582539740, "target": { "key": "9e4cf08b63f040bb0b2b7388e65c560b3be428f7d0f530a2d9949416c81b8bf1" } } ], "extra": [ 1, 230, 252, 129, 6, 25, 145, 35, 107, 193, 8, 90, 1, 16, 58, 10, 158, 13, 75, 144, 170, 253, 34, 130, 231, 23, 11, 70, 87, 89, 110, 191, 110, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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) | dinastycoin version: tesla-369