Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd4dc5c1baa4355955546b2bd6308a342e0424b960207dce397081566db087e

Tx prefix hash: d2cd11d4c6e24dfab0efa223b826834a1d79b426cde84ae119ebc080a5a3dfa3
Tx public key: 192d892b6d525dc23503160da6d7dd7ba3e25ed1dd625cdd2beaafa0332d3b4e
Timestamp: 1582098282 Timestamp [UCT]: 2020-02-19 07:44:42 Age [y:d:h:m:s]: 05:005:09:04:15
Block: 67917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156994 RingCT/type: yes/0
Extra: 01192d892b6d525dc23503160da6d7dd7ba3e25ed1dd625cdd2beaafa0332d3b4e021100000003724f989b000000000000000000

1 output(s) for total of 365.564144202000 dcy

stealth address amount amount idx
00: e32fa8fb52f5e0f2f4bb63aae0f1e689c3ac2e78ba34de5b65bfe3145a3556c5 365.564144202000 125135 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 dinasty-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": 67927, "vin": [ { "gen": { "height": 67917 } } ], "vout": [ { "amount": 365564144202, "target": { "key": "e32fa8fb52f5e0f2f4bb63aae0f1e689c3ac2e78ba34de5b65bfe3145a3556c5" } } ], "extra": [ 1, 25, 45, 137, 43, 109, 82, 93, 194, 53, 3, 22, 13, 166, 215, 221, 123, 163, 226, 94, 209, 221, 98, 92, 221, 43, 234, 175, 160, 51, 45, 59, 78, 2, 17, 0, 0, 0, 3, 114, 79, 152, 155, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8